R: @liferoad

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control

I got into a groove and went and figured out the right custom container instructions, so no stopgap required.
Did you know Beam works just fine on Alpine when the container is set up properly? (As an example.)

I got into a groove and went and figured out the right custom container instructions, so no stopgap required. Did you know Beam works just fine on Alpine when the container is set up properly? (As an example.)

I never try that but it should work.

BTW: we can also add https://cloud.google.com/dataflow/docs/guides/using-custom-containers to the md file if users need more information about custom containers.

BTW: we can also add https://cloud.google.com/dataflow/docs/guides/using-custom-containers to the md file if users need more information about custom containers.

That file just links to the page I'm already linking to. It's also weird to link to the Dataflow pages from a Beam release for a non-dataflow feature.

I mean adding this to website/www/site/content/en/documentation/runtime/environments.md if users want to learn more how to do this in general. But it is fine not to do this if you feel it is strange. :)

I don't feel it's reasonable to conflate adding that link to this PR. I have no idea where I'd put it.

I've always found our strategy of essentially putting general Beam content on the Dataflow pages to be baffling, vs improving the content on the Beam pages.